SGI Freeware 1999 August

home *** CD-ROM | disk | FTP | other *** search

/ SGI Freeware 1999 August / SGI Freeware 1999 August.iso / dist / samba.idb / usr / share / catman / u_man / cat1 / smbclient.1.Z / smbclient.1

Wrap

Text File | 1998-10-28 | 49.6 KB | 1,057 lines

SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) NNNNAAAAMMMMEEEE smbclient - ftp-like Lan Manager client program SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ssssmmmmbbbbcccclllliiiieeeennnntttt sssseeeerrrrvvvviiiicccceeeennnnaaaammmmeeee [ ppppaaaasssssssswwwwoooorrrrdddd ] [ ----EEEE ] [ ----LLLL _h_o_s_t ] [ ----MMMM _h_o_s_t ] [ ----IIII _I_P _n_u_m_b_e_r ] [ ----RRRR _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r ] [ ----NNNN ] [ ----PPPP ] [ ----UUUU _u_s_e_r_n_a_m_e ] [ ----dddd _d_e_b_u_g_l_e_v_e_l ] [ ----llll _l_o_g _b_a_s_e_n_a_m_e ] [ ----nnnn _n_e_t_b_i_o_s _n_a_m_e ] [ ----WWWW _w_o_r_k_g_r_o_u_p ] [ ----OOOO _s_o_c_k_e_t _o_p_t_i_o_n_s ] [ ----pppp _p_o_r_t _n_u_m_b_e_r ] [ ----cccc _c_o_m_m_a_n_d _s_t_r_i_n_g ] [ ----TTTT _t_a_r _o_p_t_i_o_n_s ] [ ----DDDD _i_n_i_t_i_a_l _d_i_r_e_c_t_o_r_y ] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN This program is part of the Samba suite. ssssmmmmbbbbcccclllliiiieeeennnntttt is a client that can 'talk' to a Lan Manager server. It offers an interface similar to that of the ffffttttpppp program (see ffffttttpppp(1)). Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server and so on. OOOOPPPPTTTTIIIIOOOONNNNSSSS sssseeeerrrrvvvviiiicccceeeennnnaaaammmmeeee sssseeeerrrrvvvviiiicccceeeennnnaaaammmmeeee is the name of the service you want to use on the server. A service name takes the form \\\\\\\\sssseeeerrrrvvvveeeerrrr\\\\sssseeeerrrrvvvviiiicccceeee where sssseeeerrrrvvvveeeerrrr is the netbios name of the Lan Manager server offering the desired service and sssseeeerrrrvvvviiiicccceeee is the name of the service offered. Thus to connect to the service "printer" on the Lan Manager server "lanman", you would use the servicename \\\\\\\\llllaaaannnnmmmmaaaannnn\\\\pppprrrriiiinnnntttteeeerrrr Note that the server name required is NOT necessarily the host name of the server! The name required is a Lan Manager server name, which may or may not be the same as the hostname of the machine running the server. With Samba 1.9.18p4 the server name is looked up according to the "name resolve order=" parameter in the smb.conf file, allowing an administrator to change the order and methods by which server names are looked up. ppppaaaasssssssswwwwoooorrrrdddd ppppaaaasssssssswwwwoooorrrrdddd is the password required to access the specified service on the specified server. If supplied, the ----NNNN option (suppress password prompt) is assumed. There is no default password. If no password is supplied on the command line (either here or using the ----UUUU option (see below)) and ----NNNN is not specified, the client will prompt for a password, even if the desired service does Page 1 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) not require one. (If no password is required, simply press ENTER to provide a null password.) Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password. Lowercase or mixed case passwords may be rejected by these servers. Be cautious about including passwords in scripts. ----RRRR nnnnaaaammmmeeee rrrreeeessssoooollllvvvveeee oooorrrrddddeeeerrrr This parameter will override the default name resolution order of the server listed in the "name resolve order" parameter in smb.conf. This is useful to force name resolution to take place by a particular method. This command line parameter only exists in Samba 1.9.18p4 and above. ----LLLL This option allows you to look at what services are available on a server. You use it as "smbclient -L host" and a list should appear. The ----IIII option may be useful if your netbios names don't match your tcp/ip host names or if you are trying to reach a host on another network. For example: smbclient -L ftp -I ftp.microsoft.com will list the shares available on Microsoft's public server. ----MMMM This options allows you to send messages, using the "WinPopup" protocol, to another computer. Once a connection is established you then type your message, pressing ^D (control-D) to end. If the receiving computer is running WinPopup the user will receive the message and probably a beep. If they are not running WinPopup the message will be lost, and no error message will occur. The message is also automatically truncated if the message is over 1600 bytes, as this is the limit of the protocol. One useful trick is to cat the message through ssssmmmmbbbbcccclllliiiieeeennnntttt. For example: cat mymessage.txt | smbclient -M FRED Page 2 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) will send the message in the file "mymessage.txt" to the machine FRED. You may also find the ----UUUU and ----IIII options useful, as they allow you to control the FROM and TO parts of the message. See the message command section of ssssmmmmbbbb....ccccoooonnnnffff(5) for a description of how to handle incoming WinPopup messages in Samba. Note: Copy WinPopup into the startup group on your WfWg PCs if you want them to always be able to receive messages. ----EEEE This parameter, if specified, causes the client to write messages to the standard error stream (stderr) rather than to the standard output stream. By default, the client writes messages to standard output - typically the user's tty. ----IIII _I_P _n_u_m_b_e_r _I_P _n_u_m_b_e_r represents the IP number of the server to connect to. It should be specified in standard "a.b.c.d" notation. Normally the client will attempt to locate the specified Lan Manager server by looking it up - that is, broadcasting a request for the given server to identify itself. Using this parameter will force the client to assume that the server is on the machine with the specified IP number. There is no default for this parameter. If not supplied, it will be determined automatically by the client as described above. ----NNNN If specified, this parameter suppresses the normal password prompt from the client to the user. This is useful when accessing a service that does not require a password. Unless a password is specified on the command line or this parameter is specified, the client will request a password. Page 3 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ----OOOO _s_o_c_k_e_t _o_p_t_i_o_n_s See the socket options section of ssssmmmmbbbb....ccccoooonnnnffff(5) for details. ----PPPP If specified, the service requested will be connected to as a printer service rather than as a normal filespace service. Operations such as put and get will not be applicable for such a connection. By default, services will be connected to as NON-printer services. ----UUUU _u_s_e_r_n_a_m_e _u_s_e_r_n_a_m_e is the user name that will be used by the client to make a connection, assuming your server is running a protocol that allows for usernames. Some servers are fussy about the case of this name, and some insist that it must be a valid netbios name. If no _u_s_e_r_n_a_m_e is supplied, it will default to an uppercase version of the environment variable UUUUSSSSEEEERRRR or LLLLOOOOGGGGNNNNAAAAMMMMEEEE in that order. If no _u_s_e_r_n_a_m_e is supplied and neither environment variable exists the user name will be empty. If the USER environment variable containts a '%' character, everything after that will be treated as a password. This allows you to set the environment variable to be UUUUSSSSEEEERRRR====uuuusssseeeerrrrnnnnaaaammmmeeee%%%%ppppaaaasssssssswwwwoooorrrrdddd so that a password is not passed on the command line (where it may be seen by the ps command). If the service you are connecting to requires a password, it can be supplied using the ----UUUU option, by appending a percent symbol ("%") then the password to _u_s_e_r_n_a_m_e. For example, to attach to a service as user "fred" with password "secret", you would specify ----UUUU _f_r_e_d%_s_e_c_r_e_t on the command line. Note that there are no spaces around the percent symbol. If you specify the password as part of _u_s_e_r_n_a_m_e then the ----NNNN option (suppress password prompt) is assumed. If you specify the password as a parameter AND as part of _u_s_e_r_n_a_m_e then the password as part of _u_s_e_r_n_a_m_e will take precedence. Putting nothing before or nothing after the percent symbol will cause an empty username or an empty Page 4 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) password to be used, respectively. Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password. Lowercase or mixed case passwords may be rejected by these servers. Be cautious about including passwords in scripts. ----dddd _d_e_b_u_g_l_e_v_e_l debuglevel is an integer from 0 to 5, or the letter 'A'. The default value if this parameter is not specified is zero. The higher this value, the more detail will be logged to the log files about the activities of the client. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day to day running - it generates a small amount of information about operations carried out. Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic. If the debuglevel is set to 'A' then the debug level is set to the maximum value possible (it stands for debug 'all'). ----llll _l_o_g _b_a_s_e_n_a_m_e If specified, _l_o_g _b_a_s_e_n_a_m_e specifies a base filename into which operational data from the running client will be logged. The default base name is specified at compile time. The base name is used to generate actual log file names. For example, if the name specified was "log", the following files would be used for log data: log.client.debug (containing debugging information) log.client.in (containing inbound transaction data) log.client.out (containing outbound transaction data) The log files generated are never removed by the client. Page 5 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ----nnnn _n_e_t_b_i_o_s _n_a_m_e By default, the client will use the local machine's hostname (in uppercase) as its netbios name. This parameter allows you to override the host name and use whatever netbios name you wish. ----WWWW _w_o_r_k_g_r_o_u_p Override what workgroup is used for the connection. This may be needed to connect to some servers. ----pppp _p_o_r_t _n_u_m_b_e_r port number is a positive integer value. The default value if this parameter is not specified is 139. This number is the port number that will be used when making connections to the server. The standard (well- known) port number for the server is 139, hence the default. This parameter is not normally specified. ----TTTT _t_a_r _o_p_t_i_o_n_s where _t_a_r _o_p_t_i_o_n_s consists of one or more of cccc, xxxx, IIII, XXXX, bbbb, gggg, NNNN or aaaa; used as: smbclient \\\\\\\\sssseeeerrrrvvvveeeerrrr\\\\sssshhhhaaaarrrreeee -TcxIXbgNa [ _b_l_o_c_k_s_i_z_e ] [ _n_e_w_e_r-_f_i_l_e ] _t_a_r_f_i_l_e [ _f_i_l_e_n_a_m_e_s.... ] cccc Create a tar file on UNIX. Must be followed by the name of a tar file, tape device or "-" for standard output. (May be useful to set debugging low (----dddd0000)) to avoid corrupting your tar file if using "-"). Mutually exclusive with the xxxx flag. xxxx Extract (restore) a local tar file back to a share. Unless the ----DDDD option is given, the tar files will be restored from the top level of the share. Must be followed by the name of the tar file, device or "-" for standard input. Mutually exclusive with the cccc flag. IIII Include files and directories. Is the default behaviour when _f_i_l_e_n_a_m_e_s are specified above. Causes tar files to be included in an extract or create (and therefore everything else to be excluded). See example below. Filename globbing does not work for included Page 6 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) files for extractions (yet). XXXX Exclude files and directories. Causes tar files to be excluded from an extract or create. See example below. Filename globbing does not work for excluded files (yet). bbbb Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks. gggg Incremental. Only back up files that have the archive bit set. Useful only with the cccc flag. NNNN Newer than. Must be followed by the name of a file whose date is compared against files found on the share during a create. Only files newer than the file specified are backed up to the tar file. Useful only with the cccc flag. aaaa Set archive bit. Causes the archive bit to be reset when a file is backed up. Useful with the gggg (and cccc) flags. EEEExxxxaaaammmmpppplllleeeessss smbclient \\mypc\myshare "" -N -Tx backup.tar Restore from tar file backup.tar into myshare on mypc (no password on share). smbclient \\mypc\myshare "" -N -TXx backup.tar users/docs Restore everything except users/docs smbclient \\mypc\myshare "" -N -Tc backup.tar users/docs Create a tar file of the files beneath users/docs. ----DDDD _i_n_i_t_i_a_l _d_i_r_e_c_t_o_r_y Change to initial directory before starting. Probably only of any use with the tar (----TTTT) option. ----cccc _c_o_m_m_a_n_d _s_t_r_i_n_g command string is a semicolon separated list of commands to be executed instead of prompting from stdin. ----NNNN is implied by ----cccc. Page 7 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) This is particularly useful in scripts and for printing stdin to the server, e.g. -c 'print -'. OOOOPPPPEEEERRRRAAAATTTTIIIIOOOONNNNSSSS Once the client is running, the user is presented with a prompt, "smb: \>". The backslash ("\") indicates the current working directory on the server, and will change if the current working directory is changed. The prompt indicates that the client is ready and waiting to carry out a user command. Each command is a single word, optionally followed by parameters specific to that command. Command and parameters are space-delimited unless these notes specifically state otherwise. All commands are case- insensitive. Parameters to commands may or may not be case sensitive, depending on the command. You can specify file names which have spaces in them by quoting the name with double quotes, for example "a long file name". Parameters shown in square brackets (eg., "[parameter]") are optional. If not given, the command will use suitable defaults. Parameters shown in angle brackets (eg., "<parameter>") are required. Note that all commands operating on the server are actually performed by issuing a request to the server. Thus the behaviour may vary from server to server, depending on how the server was implemented. The commands available are given here in alphabetical order. ???? PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: [_c_o_m_m_a_n_d] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: If _c_o_m_m_a_n_d is specified, the ???? command will display a brief informative message about the specified command. If no command is specified, a list of available commands will be displayed. !!!! PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: [_s_h_e_l_l _c_o_m_m_a_n_d] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: If _s_h_e_l_l _c_o_m_m_a_n_d is specified, the !!!! command will execute a shell locally and run the specified shell command. If no command is specified, a shell will be Page 8 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) run. ccccdddd PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: [_d_i_r_e_c_t_o_r_y _n_a_m_e] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: If _d_i_r_e_c_t_o_r_y _n_a_m_e is specified, the current working directory oooonnnn tttthhhheeee sssseeeerrrrvvvveeeerrrr will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible. If no directory name is specified, the current working directory oooonnnn tttthhhheeee sssseeeerrrrvvvveeeerrrr will be reported. ddddeeeellll PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_m_a_s_k> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: The client will request that the server attempt to delete all files matching _m_a_s_k from the current working directory oooonnnn tttthhhheeee sssseeeerrrrvvvveeeerrrr.... ddddiiiirrrr PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_m_a_s_k> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: A list of the files matching _m_a_s_k in the current working directory oooonnnn tttthhhheeee sssseeeerrrrvvvveeeerrrr will be retrieved from the server and displayed. eeeexxxxiiiitttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: None. DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Terminate the connection with the server and exit from the program. ggggeeeetttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_r_e_m_o_t_e _f_i_l_e _n_a_m_e> [_l_o_c_a_l _f_i_l_e _n_a_m_e] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Copy the file called _r_e_m_o_t_e _f_i_l_e _n_a_m_e from the server to the machine running the client. If specified, name the local copy _l_o_c_a_l _f_i_l_e _n_a_m_e. Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See also the lllloooowwwweeeerrrrccccaaaasssseeee command. Page 9 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) hhhheeeellllpppp PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: [_c_o_m_m_a_n_d] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: See the ???? command above. llllccccdddd PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: [_d_i_r_e_c_t_o_r_y _n_a_m_e] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: If _d_i_r_e_c_t_o_r_y _n_a_m_e is specified, the current working directory oooonnnn tttthhhheeee llllooooccccaaaallll mmmmaaaacccchhhhiiiinnnneeee will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible. If no directory name is specified, the name of the current working directory oooonnnn tttthhhheeee llllooooccccaaaallll mmmmaaaacccchhhhiiiinnnneeee will be reported. lllloooowwwweeeerrrrccccaaaasssseeee PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: None. DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Toggle lowercasing of filenames for the ggggeeeetttt and mmmmggggeeeetttt commands. When lowercasing is toggled ON, local filenames are converted to lowercase when using the ggggeeeetttt and mmmmggggeeeetttt commands. This is often useful when copying (say) MSDOS files from a server, because lowercase filenames are the norm on UNIX systems. llllssss PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_m_a_s_k> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: See the ddddiiiirrrr command above. mmmmaaaasssskkkk PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_m_a_s_k> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: This command allows the user to set up a mask which will be used during recursive operation of the mmmmggggeeeetttt and mmmmppppuuuutttt commands. The masks specified to the mmmmggggeeeetttt and mmmmppppuuuutttt commands act Page 10 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) as filters for directories rather than files when recursion is toggled ON. The mask specified with the mmmmaaaasssskkkk command is necessary to filter files within those directories. For example, if the mask specified in an mmmmggggeeeetttt command is "source*" _a_n_d the mask specified with the mmmmaaaasssskkkk command is "*.c" _a_n_d recursion is toggled ON, the mmmmggggeeeetttt command will retrieve all files matching "*.c" in all directories below and including all directories matching "source*" in the current working directory. Note that the value for _m_a_s_k defaults to blank (equivalent to "*") and remains so until the mmmmaaaasssskkkk command is used to change it. It retains the most recently specified value indefinitely. To avoid unexpected results it would be wise to change the value of _m_a_s_k back to "*" after using the mmmmggggeeeetttt or mmmmppppuuuutttt commands. mmmmdddd PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_d_i_r_e_c_t_o_r_y _n_a_m_e> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: See the mmmmkkkkddddiiiirrrr command. mmmmggggeeeetttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_m_a_s_k> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Copy all files matching _m_a_s_k from the server to the machine running the client. Note that _m_a_s_k is interpreted differently during recursive operation and non-recursive operation - refer to the rrrreeeeccccuuuurrrrsssseeee and mmmmaaaasssskkkk commands for more information. Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See also the lllloooowwwweeeerrrrccccaaaasssseeee command. mmmmkkkkddddiiiirrrr PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_d_i_r_e_c_t_o_r_y _n_a_m_e> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Create a new directory oooonnnn tttthhhheeee sssseeeerrrrvvvveeeerrrr (user access privileges permitting) with the specified name. mmmmppppuuuutttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_m_a_s_k> Page 11 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Copy all files matching _m_a_s_k in the current working directory oooonnnn tttthhhheeee llllooooccccaaaallll mmmmaaaacccchhhhiiiinnnneeee to the current working directory on the server. Note that _m_a_s_k is interpreted differently during recursive operation and non-recursive operation - refer to the rrrreeeeccccuuuurrrrsssseeee and mmmmaaaasssskkkk commands for more information. Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. pppprrrriiiinnnntttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_f_i_l_e _n_a_m_e> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Print the specified file ffffrrrroooommmm tttthhhheeee llllooooccccaaaallll mmmmaaaacccchhhhiiiinnnneeee through a printable service on the server. See also the pppprrrriiiinnnnttttmmmmooooddddeeee command. pppprrrriiiinnnnttttmmmmooooddddeeee PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_g_r_a_p_h_i_c_s _o_r _t_e_x_t> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Set the print mode to suit either binary data (such as graphical information) or text. Subsequent pppprrrriiiinnnntttt commands will use the currently set print mode. pppprrrroooommmmpppptttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: None. DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Toggle prompting for filenames during operation of the mmmmggggeeeetttt and mmmmppppuuuutttt commands. When toggled ON, the user will be prompted to confirm the transfer of each file during these commands. When toggled OFF, all specified files will be transferred without prompting. ppppuuuutttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_l_o_c_a_l _f_i_l_e _n_a_m_e> [_r_e_m_o_t_e _f_i_l_e _n_a_m_e] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Copy the file called _l_o_c_a_l _f_i_l_e _n_a_m_e from the machine running the client to the server. If specified, name the remote copy _r_e_m_o_t_e _f_i_l_e _n_a_m_e. Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See also the Page 12 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) lllloooowwwweeeerrrrccccaaaasssseeee command. qqqquuuueeeeuuuueeee PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: None. DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Displays the print queue, showing the job id, name, size and current status. qqqquuuuiiiitttt PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: None. DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: See the eeeexxxxiiiitttt command. rrrrdddd PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_d_i_r_e_c_t_o_r_y _n_a_m_e> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: See the rrrrmmmmddddiiiirrrr command. rrrreeeeccccuuuurrrrsssseeee PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: None. DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Toggle directory recursion for the commands mmmmggggeeeetttt and mmmmppppuuuutttt. When toggled ON, these commands will process all directories in the source directory (i.e., the directory they are copying _f_r_o_m) and will recurse into any that match the mask specified to the command. Only files that match the mask specified using the mmmmaaaasssskkkk command will be retrieved. See also the mmmmaaaasssskkkk command. When recursion is toggled OFF, only files from the current working directory on the source machine that match the mask specified to the mmmmggggeeeetttt or mmmmppppuuuutttt commands will be copied, and any mask specified using the mmmmaaaasssskkkk command will be ignored. rrrrmmmm PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_m_a_s_k> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Remove all files matching _m_a_s_k from the current working directory oooonnnn tttthhhheeee sssseeeerrrrvvvveeeerrrr.... Page 13 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) rrrrmmmmddddiiiirrrr PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_d_i_r_e_c_t_o_r_y _n_a_m_e> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Remove the specified directory (user access privileges permitting) ffffrrrroooommmm tttthhhheeee sssseeeerrrrvvvveeeerrrr.... ttttaaaarrrr PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss:::: <_c|_x>[_I_X_b_g_N_a] DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn:::: Performs a tar operation - see the ----TTTT command line option above. Behaviour may be affected by the ttttaaaarrrrmmmmooooddddeeee command (see below). Using g (incremental) and N (newer) will affect tarmode settings. Note that using the "-" option with tar x may not work - use the command line option instead. bbbblllloooocccckkkkssssiiiizzzzeeee PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss <_b_l_o_c_k_s_i_z_e> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks. ttttaaaarrrrmmmmooooddddeeee PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss <_f_u_l_l|_i_n_c|_r_e_s_e_t|_n_o_r_e_s_e_t> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn Changes tar's behaviour with regard to archive bits. In full mode, tar will back up everything regardless of the archive bit setting (this is the default mode). In incremental mode, tar will only back up files with the archive bit set. In reset mode, tar will reset the archive bit on all files it backs up (implies read/write share). sssseeeettttmmmmooooddddeeee PPPPaaaarrrraaaammmmeeeetttteeeerrrrssss <_f_i_l_e_n_a_m_e> <_p_e_r_m=[+|-]_r_s_h_a> DDDDeeeessssccccrrrriiiippppttttiiiioooonnnn A version of the DOS attrib command to set file permissions. For example, setmode myfile +r Page 14 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) would make myfile read only. NNNNOOOOTTTTEEEESSSS Some servers are fussy about the case of supplied usernames, passwords, share names (aka service names) and machine names. If you fail to connect try giving all parameters in uppercase. It is often necessary to use the ----nnnn option when connecting to some types of servers. For example OS/2 LanManager insists on a valid netbios name being used, so you need to supply a valid name that would be known to the server. ssssmmmmbbbbcccclllliiiieeeennnntttt supports long file names where the server supports the LANMAN2 protocol. FFFFIIIILLLLEEEESSSS Not applicable. EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS UUUUSSSSEEEERRRR The variable USER may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. IIIINNNNSSSSTTTTAAAALLLLLLLLAAAATTTTIIIIOOOONNNN The location of the client program is a matter for individual system administrators. The following are thus suggestions only. It is recommended that the client software be installed under the /usr/local/samba hierarchy, in a directory readable by all, writeable only by root. The client program itself should be executable by all. The client should NOT be setuid or setgid! The client log files should be put in a directory readable and writable only by the user. To test the client, you will need to know the name of a running Lan manager server. It is possible to run ssssmmmmbbbbdddd (see ssssmmmmbbbbdddd(8)) as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server. VVVVEEEERRRRSSSSIIIIOOOONNNN This man page is (mostly) correct for version 1.9.00 of the Samba suite, plus some of the recent patches to it. These notes will necessarily lag behind development of the client software, so it is possible that your version of the client has extensions or parameter semantics that differ from or Page 15 (printed 10/26/98) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) ssssmmmmbbbbcccclllliiiieeeennnntttt 1111....9999....11118888pppp11110000 ((((22220000 AAAAuuuugggg 1111999999998888)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) are not covered by this man page. Please notify these to the address below for rectification. SSSSEEEEEEEE AAAALLLLSSSSOOOO ssssmmmmbbbbdddd(8) DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS [This section under construction] Most diagnostics issued by the client are logged in a specified log file. The log file name is specified at compile time, but may be overridden on the command line. The number and nature of diagnostics available depends on the debug level used by the client. If you have problems, set the debug level to 3 and peruse the log files. Most messages are reasonably self-explanatory. Unfortunately, at time of creation of this man page the source code is still too fluid to warrant describing each and every diagnostic. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing. BBBBUUUUGGGGSSSS None known. CCCCRRRREEEEDDDDIIIITTTTSSSS The original Samba software and related utilities were created by Andrew Tridgell (samba-bugs@samba.anu.edu.au). Andrew is also the Keeper of the Source for this project. See ssssmmmmbbbb....ccccoooonnnnffff(5) for a full list of contributors and details on how to submit bug reports, comments etc. Page 16 (printed 10/26/98)